Otherwise depending on bilateral agreement or intra-domain policy the current
time is noted as the message arrival time and the message is held until expiration
of the deferred-delivery-time. The message and timestamp are then returned as
result. The procedure then terminates.
domain is added with relay as action. If an arrival time accompanies the
message, then delivery deferral has occured and deferred-time is set to the current time
and arrival-time is set to the accompanying timestamp value. Otherwise no
deferral has occured and the arrival-time is set to the current time.
3) If any of the extension fields is marked critial for relaying but is not
semantically understood by the MTA, the procedure returns a report generation
instruction. The non-delivery-reason-code is set to transfer-failure and the non-delivery-diagnostic-code to unsupported-critical-function. The procedure then
terminates.
Note - This procedure may be called multiple times for any particular message.
In such cases, the procedure ignores per recipient instructions generated by
previous calls to this procedure which have not yet been acted upon elsewhere.
If the per recipient instruction indicates a delivery failure, then the value
for Originator-requested-alternate-recipient is examined for possible recipient
substitution. If an alternate recipient is determined and no security parameters are
violated, then a redirection instruction is generated and the procedure
terminates.
Otherwise the procedure returns a report generation instruction for this
recipient. The non-delivery-reason-code and non-delivery-diagnostic-code are those
supplied by the Message-delivery or Report-delivery procedure. The procedure then
terminates.
recipient. If not, the value for Originator-requested-alternate-recipient is
examined for possible recipient substitution. If this reveals no alternate
recipient, the the value for alternate-recipient-allowed and any MD specified alternate
recipient are considered. If an alternate recipient is determined and no security
parameters are violated, then a redirection instruction is generated and the
procedure terminates.
Otherwise the procedure returns a report generation instruction for this
recipient.
- 7 -
AP IX-56-E
assigned- reassignment-
- 8 -
AP IX-56-E
using the recipient-name from argument 2 to form the intended-recipient-name,
obtaining the redirection-reason from argument 4 and containing the Time at which
this redirection is performed. The OR-name supplied in the first argument is then
substituted for that recipient-name.
3) In the other-actions field the current trace-information, the value
redirected is set to true.
4) The message transfer envelope is updated as follows:
recipient-name: replaced
trace-information: indicate redirected
redirection-history: append previous
recipient-name and
redirection-reason
originator-requested-alternate-recipient: deleted if, and only if the
redirection-reason indicates
originator-requested-
alternate-recipient.
8) If the new report request values (determined in step 5) or the DL's local
policy will prevent the originator from receiving a requested delivery report
from the DL's members, then a copy of the message, with delivery report request
instructions for the expanded DL, is constructed and returned along with the message.
9) The procedure returns the revised message and the optional report request
and then terminates.
for which 0 < j </=p the associated trace info element is [MD(j) relayed, op(j)]
and op(j) = nil. That is, a loop is detected if M arrives at an MD which has
already relayed it and each MD afterwards has also relayed it without performing any
operation other than routing. If a loop is detected, then the algorithm returns
an error indicating the problem, and terminates.
If the report is not to be suppressed, the MTA then replaces the OR-name
currently in the report-destination-name field by the OR-name immediately preceding that
one in the originator-and-DL-expansion-history field. Thus the report acquires,
as a new destination, the next entry back along the chain of entries in the
originator-and-DL-expansion-history field:
4) If authentication is not required Messages-waiting is returned if the MTS-user subscribes to the Hold for Delivery element-of-service, and the procedure
terminates.
In the case of recipient-name the MTA may use the requested-delivery-method, if
present, as an indication of which form of OR-address the directory-name should
be mapped to. If a form of OR-address appropriate to the request-delivery-method
cannot be found, the recipient-improperly-specified abstract-error is returned by
the MTA.
c) If a recipient-name contains an OR-address of a form not appropriate to
the requested-delivery-method, if present, the recipient-improperly-specified
abstract-error is returned by the MTA.
1) An empty or, if requested, a proof-of-delivery and optional recipient-
certificate result passed back from the MTS-user as an indication of successful
delivery with no reporting requirements.
2) If a report is required, the main module is invoked and passed the
message with per-recipient instructions describing any delivery problems encountered
and/or indicating successful deliveries to be reported on.
unable-to-transfer and unsupported-critical-function respectively.
- 9 -
AP IX-56-E
then, subject to the security policy, a report instruction for this recipient is
generated. The values of non-delivery-reason-code and non-delivery-diagnostic-
code are unable-to-transfer and secure-messaging-error respectively.
6) If delivery is barred by restrictions imposed in a previously invoked
Register or Delivery-control abstract-operation, then, subject to the security-
policy in force, the MAT will hold the message pending the lifting of the applicable
restriction(s).
8) If restricted delivery is enforced, and the recipient falls in the
category of unauthorized senders, then a report instruction is generated for this
recipient. The value of non-delivery-reason-code is set to restricted- delivery.
Processing then terminates for this recipient.
unable-to-transfer and unsupported-critical-function respectively.
security-policy, then the report is discarded.
2) If Report delivery is barred by restrictions imposed in a previously
invoked Register or Delivery-control abstract-operation, then, subject to the
security-policy in force, the MAT will hold the report pending the lifting of the
applicable restriction(s). Restrictions are established by arguments of the Delivery-control or Register abstract-operation as described in